home *** CD-ROM | disk | FTP | other *** search
- From: Rich Paul <rpaul@trcinc.com>
- Message-ID: <3147413B.B10@trcinc.com>
- X-Original-Date: Wed, 13 Mar 1996 16:42:19 -0500
- Path: in2.uu.net!bounce-back
- Date: 13 Mar 96 23:46:01 GMT
- Approved: fjh@cs.mu.oz.au
- Newsgroups: comp.std.c++
- Subject: Implementation of class basic_string<class charT, class traits, class Allocator>
- Organization: Technical Resource Connection
- X-Mailer: Mozilla 2.0 (WinNT; I)
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBFAgUBMUdeWOEDnX0m9pzZAQFWmQF/dBiv+VHMe+viJZmvWyyfmbwOVgV74Kne
- IiYXsYC2S1lqpaq2kcfAtsFxZs173y67
- =A49f
-
- I am currently implementing, from the working paper, class
- basic_string. I'm not sure on a couple of things. The first is
- if the standard says:
-
- insert ( const basic_string bs&str )
- Does this and that
- insert ( charT *cp )
- insert ( basic_string ( cp );
-
- am I non-complient if I put the real code in the charT* overload
- and have the other call it? I'm not sure the level of
- complience that is required ...
-
- Also, is there a validation suite that can put this class
- through it's paces?
-
- One more thing ... before calling traits::deallocate, should I
- explicitly call destructors on the charT's in my array, since it
- may be a class type, or does the definition of charT as being
- 'char-like' preclude this?
- ---
- [ comp.std.c++ is moderated. To submit articles: try just posting with ]
- [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ]
- [ FAQ: http://reality.sgi.com/employees/austern_mti/std-c++/faq.html ]
- [ Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
- [ Comments? mailto:std-c++-request@ncar.ucar.edu ]
-